feat(jetbrains): add Junie context integration and IDE onboarding docs#7
feat(jetbrains): add Junie context integration and IDE onboarding docs#7JustAGhosT merged 1 commit intomainfrom
Conversation
- Add optional Junie dependency in plugin.xml (loaded only when Junie is installed) - Add junie.xml descriptor registering RetortWorkspaceContextService - Implement RetortWorkspaceContextService to build phase/task/teams context block - Rename CI workflow to "JetBrains Plugin", add workflow_dispatch trigger - Add docs/onboarding/ with per-IDE guides (VS Code, JetBrains, Zed) and overview Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Mention Blocks like a regular teammate with your question or request: @blocks review this pull request Run |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
Disabled knowledge base sources:
📝 WalkthroughWalkthroughThe PR expands Retort IDE plugin support across multiple editors (JetBrains, VS Code, Zed), adds Junie AI integration for workspace context injection to JetBrains/IntelliJ-based IDEs, includes comprehensive onboarding documentation, and updates CI/CD verification for cross-IDE compatibility testing. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related issues
Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 01ee9ecf57
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ?.mapNotNull { f -> | ||
| try { | ||
| val text = f.readText() | ||
| if (text.contains(""""status":"working"""") || text.contains(""""status":"accepted"""")) { |
There was a problem hiding this comment.
Parse task status via JSON before filtering in-progress tasks
buildContext() currently treats a task as in-progress only when the raw file text contains the exact substrings "status":"working" or "status":"accepted"; this misses valid JSON that includes whitespace (for example "status": "working"), so active tasks are silently dropped from injected context. Parsing the task JSON (or using a whitespace-tolerant status matcher) would avoid false negatives for formatted task files.
Useful? React with 👍 / 👎.
Summary
RetortWorkspaceContextServiceto inject active phase, tasks, and teams context into Junie AI sessionsdocs/onboarding/with per-IDE guides for VS Code, JetBrains (PyCharm/IDEA/Rider), and Zedworkflow_dispatchtriggerTest plan
cd extensions/pycharm && ./gradlew buildPluginRetortWorkspaceContextServiceregisters as project servicedocs/onboarding/guides for accuracy🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
New Features
Improvements